Add Expr::try_as_col
, deprecate Expr::try_into_col
(speed up optimizer)
#10448
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Part of #9637
I ran into this while working on #10444
Rationale for this change
There are places in the code that check if an expr is a column by using
Expr::try_into_col()
which has two potential performance problems:Column
(and thus a string) to check if an expr is aExpr::Column
DataFusionError
to check if an expr is not aExpr::Column
What changes are included in this PR?
Expr::try_as_col
Expr::try_into_col
Expr::try_into_col
Are these changes tested?
By existing tests
Are there any user-facing changes?
A new function / less required copying
I doubt we will see any significant performance changes however it does reduce allocations during planning